Indirect user authentication

ABSTRACT

As disclosed herein a computer system, executed by a computer, includes receiving, from a user, a request for access to a shared system, wherein the request comprises a user identifier and a user password corresponding to the user, and determining privileges corresponding to the shared system using the user identifier. The computer system further includes requesting, from an identity manager, a shared identifier and a shared password corresponding to the shared system, receiving, from the identity manager, the shared identifier and the shared password, and using the shared identifier and the shared password to enable the user to use the shared system.

BACKGROUND

The present invention relates to user authentication, and moreparticularly to indirect user authentication.

In computing, user access to a computing system is controlled usingidentity management. Identity management is the process of controllinginformation about user accounts corresponding to the computer. Userinformation may include details such as information that authenticates(i.e., verifies) the identity of a user, information that describesprivileges and authorities the user is entitled to, and the like. A usercan authenticate his identity to the computer by providing hisauthentication credentials. Authentication credentials may include auser ID and a password that have been assigned to uniquely identify theuser.

Privileged identity management focuses on the special requirements ofcontrolling access to powerful user accounts (i.e., privileged user IDs)within the information technology (IT) infrastructure of a company. As ageneral rule, IT organizations prefer to limit the number of privilegeduser IDs created on a system (e.g., one administrator user ID, one userID with application deploy authority, etc). With only one administratoruser ID, all users with authority to perform administrative tasks sharethe administrator user ID and password. Similarly, other privileged userIDs and passwords may be shared in the same way.

SUMMARY

As disclosed herein, a computer system, executed by a computer, includesreceiving, from a user, a request for access to a shared system, whereinthe request comprises a user identifier and a user passwordcorresponding to the user, and determining privileges corresponding tothe shared system using the user identifier. The computer system furtherincludes requesting, from an identity manager, a shared identifier and ashared password corresponding to the shared system, receiving, from theidentity manager, the shared identifier and the shared password, andusing the shared identifier and the shared password to enable the userto use the shared system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram depicting a computing environmentin accordance with at least one embodiment of the present invention;

FIG. 2 is a flowchart depicting a shared user ID method, in accordancewith at least one embodiment of the present invention;

FIG. 3 is a flowchart depicting an authorization detection method, inaccordance with at least one embodiment of the present invention; and

FIG. 4 is a block diagram depicting various components of one embodimentof a computer suitable for executing the methods disclosed herein.

DETAILED DESCRIPTION

Privileged user IDs corresponding to a computer system may have systemprivileges and authorities beyond that of an ordinary user of thecomputer system. The activities and operations performed by a privilegeduser ID may be logged in command logs, activity logs, and the like.However, if a privileged user ID and password have been shared, there isno way of confirming which user may have been using the privileged userID at any given time.

If an audit or monitoring operation detects suspicious activitycorresponding to a privileged user ID, and the privileged user ID hasbeen shared, there may be no way to identify the user responsible forthe suspicious activity. It has been determined that there is a need toprovide auditable indirect user authentication, allowing authorizedusers to share a privileged user ID without having direct access to thepassword corresponding to the privileged user ID. Additionally, whenevera privileged user ID is shared, it should be confirmed that the user ofthe shared user ID has followed the proper procedures to gain accessedto the computer system. The embodiments disclosed herein generallyaddress the above-described problems.

The present invention will now be described in detail with reference tothe Figures. FIG. 1 is a functional block diagram depicting a computingenvironment 100 in accordance with an embodiment of the presentinvention. Computing environment 100 includes servers 110, 120, and 130,client 140 and privileged system 150 which can be smart phones, tablets,desktop computers, laptop computers, specialized computer servers, orany other computer systems known in the art capable of communicatingover network 190. In some embodiments, servers 110, 120, and 130represent computer systems utilizing clustered computers and componentsto act as a single pool of seamless resources when accessed throughnetwork 190. In general, servers 110, 120, and 130, client 140 andprivileged system 150 are representative of any electronic devices, orcombination of electronic devices, capable of executing machine-readableprogram instructions, as described in greater detail with regard to FIG.4.

As depicted, server 110 includes access manager 112, persistent storage114, and shared user ID module 116. Shared user ID module 116 may beconfigured to monitor and manage requests for access to shared user IDs.A shared user ID may be a user ID that is used by more than one user andmay have system level access privileges or greater authority than thatof an ordinary user. Access manager 112 may be configured to manageauthentication and authorization of user ID requests for resources(e.g., web services, operating systems, and existing applications). Ifshared user ID module 116 detects a request for a shared user ID from aclient 140, then shared user ID module 116 may pass the request toaccess manager 112 for continued processing. Access manager 112 maydetermine if the user logged into client 140 is authorized to use theshared user ID.

In some embodiments, a user requests a specific shared user ID onprivileged system 150. In other embodiments, a user requests privilegedaccess to privileged system 150, without specifying a specific user ID,and access manager 112 provides a shared user ID that corresponds to theauthorizations assigned to the requesting user ID. Shared user ID module116 may receive from access manager 112 the shared user ID and thepassword corresponding to the shared user ID. All activitiescorresponding to access manager 112 and shared user ID module 116 mayretained in log files and stored on persistent storage 114.

As depicted, server 120 includes identity manager 122 and persistentstorage 124. Identity manager 122 (sometimes referred to as a passwordvault) may be a registry of passwords corresponding to shared user IDs,and may be implemented as a software solution, a hardware solution, or acombination of the two. Identity manager 122 may provide additionalsecurity by encrypting the stored passwords. The user ID information(e.g., the user ID, user ID privileges, and password) as well asactivity logs may be stored on persistent storage 124.

As depicted, server 130 includes activity monitor 132 and persistentstorage 134. Activity monitor 132 monitors computing systems attached tonetwork 190, such as privileged system 150 and others (not shown), todetect access via a shared user IDs. If activity monitor 132 detectssuspicious activity corresponding to a shared user ID (e.g., the user ofthe shared user ID did not did not follow a required protocol for orprocedures to gain access to privileged system 150), then activitymonitor 132 may take actions to prohibit the user from accessingprivileged system 150, such as, forcefully terminating the sessionassociated with the shared user ID, sending alerts to an administratoror security group, and generating detailed log information such as,login time, connection client information, identifying the detectedactivity, and the like. Activity monitor 132 may retain, on persistentstorage 134, logs containing details of detected use of shared user IDs.The recorded information may include, but is not limited to, the shareduser ID, the name of the individual using the shared user ID, the loginand logout times, and all commands issued. When performing monitoringoperations, activity monitor 132 my access log information frompersistent storage 114 (access manager 112), persistent storage 124(identity manager 122), and persistent storage 154 (privileged system150).

Persistent storage 114, 124, 134, and 154 may be any non-volatilestorage media known in the art. For example, persistent storage 114,124, 134, and 154 can be implemented with a tape library, opticallibrary, one or more independent hard disk drives, or multiple hard diskdrives in a redundant array of independent disks (RAID). Similarly, dataon persistent storage 114 may conform to any suitable storagearchitecture known in the art, such as a file, a relational database, anobject-oriented database, and/or one or more tables.

Servers 110, 120, and 130, client 140, privileged system 150, and otherelectronic devices (not shown) communicate over network 190. Network 190can be, for example, a local area network (LAN), a wide area network(WAN) such as the Internet, or a combination of the two, and includewired, wireless, or fiber optic connections. In general, network 190 canbe any combination of connections and protocols that will supportcommunications between Servers 110, 120, and 130, client 140, andprivileged system 150, in accordance with an embodiment of the presentinvention.

FIG. 2 is a flowchart depicting a shared user ID method 200, inaccordance with at least one embodiment of the present invention. Asdepicted, shared user ID method 200 includes receiving (210) a requestfor shared user ID access to a system, determining (220) allowableprivileges, requesting (230) a shared user ID and password, receiving(240) a shared user ID and password, and using (250) a shared user IDand password to enable the user to use a system. Shared user ID method200 enables a shared ID module (e.g. shared user ID module 116) tomanage and monitor access to shared user IDs.

Receiving (210) a request for shared user ID access to a system mayinclude shared user ID module 116 receiving a request for shared user IDaccess to a computer system (e.g., privileged system 150). The requestmay be initiated from a user logged into a client computer (e.g., client140). In some embodiments, the user initiates the request for shareduser ID access by authenticating (e.g. providing a user ID and password)with shared user ID module 116. The authentication operation may verifythe identity of the requester. In other embodiments, shared user IDmodule 116 verifies the identity of the requester by obtaining detailsof the logged in user from client 140.

Determining (220) allowable privileges may include shared user ID module116 using the verified identity of the user requesting privileged accessto determine if the requesting user is authorized to use a shared ID. Insome embodiments, a user requests to use a specific shared user ID onprivileged system 150, and shared user ID module 116 uses the verifiedidentity of the requesting user to determine if the requesting user isauthorized to use the requested shared user ID. In other embodiments, auser requests privileged access to privileged system 150 (withoutrequesting a specific ID), and shared user ID module 116 uses theverified identity of the requesting user to determine an appropriateshared user ID with privileges that correspond to the privileges therequesting user is authorized to have.

In one embodiment, share ID module 116 performs the operations todetermine if a requesting user is authorized to use a shared user ID. Inanother embodiment, share ID module 116 requests that an access manager(e.g., access manager 112) perform the operations to determine if therequesting user is authorized to use a shared user ID. The operations todetermine if a requesting user is authorized to use a shared user ID aredescribed in greater detail in the description of FIG. 3. If it isdetermined that the requesting user is not authorized to use the sharedID, then the request is denied, and no further processing occurs.

Requesting (230) a shared user ID and password may include shared userID module 116 requesting that an access manager (e.g. access manager112) provide the login credentials for a specific shared user ID. Insome embodiments, shared user ID module 116 requests the shared user IDand password from access manager 112. In other embodiments, shared userID module 116 requests the shared user ID from access manager 112, andrequests the password corresponding to the share user ID from identitymanager 122.

Receiving (240) a shared user ID and password may include shared user IDmodule 116 receiving login credentials corresponding to a shared userID. In some embodiments, the login credentials include a shared user IDand an encrypted password. In other embodiments, the login credentialsinclude a shared user ID and a plain text password. In one embodiment,shared user ID module 116 receives an indication that the shared user IDis currently unavailable (e.g., the shared user ID is currently in use).If the shared user ID is unavailable, the request is terminated and aninformative message is provided to the user. In another embodiment, theshared user ID is available (i.e., it is not currently in use) andaccess manager 112 obtains the password from identity manager 122 andprovides both the shared user ID and password to shared user ID module116. In yet another embodiment, shared user ID module 116 receives theshared user ID from access manager 112, and receives the passwordcorresponding to the shared user ID from identity manager 122.

Using (250) a shared user ID and password to enable the user to use asystem may include shared user ID module 116 providing the shared userID to the user. In some embodiments, shared user ID module 116 providesthe shared user ID to client 140. In other embodiments, shared user IDmodule 116 automatically initiates the login procedure on behalf ofclient 140 without providing the share user ID to client 140. In anotherembodiment, the user begins the login operation on client 140 using theprovided shared user ID. Then privileged system 150 requests thepassword from shared user ID module 116, and shared user ID module 116provides the encrypted password to privileged system 150 without theuser having access to the password. To assure controlled access to theshared user ID, shared user ID module 116 may never expose, to client140, the password corresponding to the share user ID to client 140.

When shared user ID module 116 grants a user permission to use a shareduser ID, the duration of the authorization may be limited. In oneembodiment, the authority is limited to a single login session and ifadditional login sessions are require, a new shared user ID request isrequired for each session. In other embodiments, there is a time limitassociates with the granted authority. For example, the session loginmust occur within 10 minutes of approval and cannot continue for morethan 2 hours. Throughout the operation of shared user ID method 200,logs may be maintained to enable auditing and reporting operations (e.g.generating a report listing the users who have requested access tospecific shared user IDs). Depending on the operation, the logs may bestored on persistent storage, such as persistent storage 114, 124, 134,and/or 154.

FIG. 3 is a flowchart depicting an authorization detection method 300,in accordance with at least one embodiment of the present invention. Asdepicted, authorization detection method 300 includes receiving (310) arequest to access a shared user ID, determining (320) whether the useris included in an authorized user list, determining (330) whether theuser is a member of an authorized user group, determining (340) whetherthe user's user ID contains appropriate privileges, denying (350) theaccess request, and approving (360) the access request. Authorizationdetection method 300 determines if a user ID has the authority to accessa shared user ID. The depicted embodiment of authorization detectionmethod 300 contains three decision operations, however, otherembodiments of authorization detection method 300 may contain a subsetof the depicted decision operations, none of the depicted decisionoperations, additional decision operation, or a combination thereof.

Receiving (310) a request to access a shared user ID may includereceiving a request that includes: (i) the system on which a share userID is being requested (the shared system), (ii) the shared user ID beingrequested, and (iii) credentials that identify the user making therequest (the requesting user). In some embodiments, the request does notcontain credentials identifying the requesting user, and the requestinguser is presented with a challenge allowing the requesting user toidentify himself by providing a user ID and password. In otherembodiments, the credentials (e.g., a user ID, employee serial number,or the like) that uniquely identify the requesting user are provided asa part of the request.

Determining (320) whether the user is included in an authorized userlist may include retrieving, from persistent storage (e.g., persistentstorage 114, or 154), a predetermined list of users that have beenapproved to be given access to the requested shared user ID on theshared system. In some embodiments, the authorized user list comprisesuser IDs. In other embodiments, the authorized user list comprisesemployee serial numbers. If the credentials of the requesting user arecontained in the authorized user list corresponding to the sharedsystem, then authorization detection method 300 proceeds to approving(360) the access request. Otherwise, the method proceeds to determiningoperation 330.

Determining (330) whether the user is a member of an authorized usergroup may include identifying a privileged user group the requestedshared user ID belongs to. If the user ID of the requesting user is alsoin the privileged user group, then authorization detection method 300proceeds to approving (360) the access request. Otherwise, the methodproceeds to determining operation 340.

Determining (340) whether the user's user ID contains appropriateprivileges may include analyzing the privileges associated with the userID of the requesting user. In some environments, for ownership reasons,it is required that a specific user ID perform all privilegedoperations. If the user ID identified by the credentials of therequesting user contains at least the same level of authorization as theshared user ID being requested, then authorization detection method 300proceeds to approving (360) the access. Otherwise, the method proceedsto denying (350) the access request.

Denying (350) the access request may include terminating authorizationdetection method 300, and notifying the user the request has beendenied. In some embodiments, the requesting user is presented with anerror message indicating that the user ID is not authorized to use therequested shared user ID. In other embodiments, an email, identifyingthe user and the shared user ID in the failed attempt, is sent toappropriate administrative and security organizations. In anotherembodiment, the failed attempt is recorded in an activity log. Theactivity log may be retained on persistent storage (e.g., persistentstorage 114).

Approving (360) the access request may include notifying the requesterthat the requesting user is authorized to us the requested shared userID on the shared system. In some embodiments, the approval is recordedin an activity log. The activity log may be retained on persistentstorage (e.g., persistent storage 114). Authorization detection method300 has run to a successful completion.

FIG. 4 depicts a block diagram of components of a computer system 400,which is an example of systems such as Servers 110, 120, and 130, client140, privileged system 150 within computing environment 100 of FIG. 1,in accordance with an embodiment of the present invention. It should beappreciated that FIG. 4 provides only an illustration of oneimplementation and does not imply any limitations with regard to theenvironments in which different embodiments can be implemented. Manymodifications to the depicted environment can be made.

Servers 110, 120, and 130, client 140, and privileged system 150 includeprocessor(s) 404, cache 414, memory 406, persistent storage 408,communications unit 410, input/output (I/O) interface(s) 412 andcommunications fabric 402. Communications fabric 402 providescommunications between cache 414, memory 406, persistent storage 408,communications unit 410, and input/output (I/O) interface(s) 412.Communications fabric 402 can be implemented with any architecturedesigned for passing data and/or control information between processors(such as microprocessors, communications and network processors, etc.),system memory, peripheral devices, and any other hardware componentswithin a system. For example, communications fabric 402 can beimplemented with one or more buses.

Memory 406 and persistent storage 408 are computer readable storagemedia. In this embodiment, memory 406 includes random access memory(RAM). In general, memory 406 can include any suitable volatile ornon-volatile computer readable storage media. Cache 414 is a fast memorythat enhances the performance of processor(s) 404 by holding recentlyaccessed data, and data near recently accessed data, from memory 406.

Program instructions and data used to practice embodiments of thepresent invention, e.g., shared user ID method 200 and authorizationdetection method 300 are stored in persistent storage 408 for executionand/or access by one or more of the respective processor(s) 404 viacache 414. In this embodiment, persistent storage 408 includes amagnetic hard disk drive. Alternatively, or in addition to a magnetichard disk drive, persistent storage 408 can include a solid-state harddrive, a semiconductor storage device, a read-only memory (ROM), anerasable programmable read-only memory (EPROM), a flash memory, or anyother computer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 408 may also be removable. Forexample, a removable hard drive may be used for persistent storage 408.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage408.

Communications unit 410, in these examples, provides for communicationswith other data processing systems or devices, including resources ofservers 110, 120, and 130, client 140, and privileged system 150. Inthese examples, communications unit 410 includes one or more networkinterface cards. Communications unit 410 may provide communicationsthrough the use of either or both physical and wireless communicationslinks. Program instructions and data used to practice embodiments ofshared user ID method 200 and authorization detection method 300 may bedownloaded to persistent storage 408 through communications unit 410.

I/O interface(s) 412 allows for input and output of data with otherdevices that may be connected to each computer system. For example, I/Ointerface(s) 412 may provide a connection to external device(s) 416 suchas a keyboard, a keypad, a touch screen, a microphone, a digital camera,and/or some other suitable input device. External device(s) 416 can alsoinclude portable computer readable storage media such as, for example,thumb drives, portable optical or magnetic disks, and memory cards.Software and data used to practice embodiments of the present inventioncan be stored on such portable computer readable storage media and canbe loaded onto persistent storage 408 via I/O interface(s) 412. I/Ointerface(s) 412 also connect to a display 418.

Display 418 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A computer system comprising: one or morecomputer processors; one or more computer readable storage media;program instructions stored on the computer readable storage media forexecution by at least one of the computer processors, the programinstructions comprising instructions for: receiving, from one or moreusers, a request for access to a shared system, wherein the requestcomprises a shared system identifier that indicates the shared systemfor which access is being requested, a shared user identifier, and auser identifier and a user password corresponding to the one or moreusers; determining if the one or more users are authorized to access theshared system by confirming the user identifier of each of the one ormore users includes at least the same level of authorization as theshared user identifier and one or more of: confirming the one or moreusers are included in an authorized user list, and confirming the one ormore users are a member of an authorized user group; responsive todetermining that the one or more users are authorized to access theshared system, requesting, from an identity manager, the shared useridentifier and a shared password corresponding to the shared system;receiving, from the identity manager, the shared user identifier and theshared password, and providing the shared user identifier to each of theone or more users, and automatically authenticating each of the one ormore users on the shared system using the shared user identifier and theshared password; using the shared user identifier and the sharedpassword of each of the one or more users to enable the one or moreusers to use the shared system, wherein the shared password is notprovided to the any of the one or more users; and retaining detailscorresponding to the request for access to the shared system by the oneor more users in one or more logs, analyzing the one or more logs todetermine that a particular user of the shared system is accessing theshared system without following a required protocol to gain access,prohibiting access to the shared system by the particular user byterminating an active session of the particular user, and sending analert to a security administrator, wherein the alert comprises one ormore of login time of the particular user, connection client informationcorresponding to the particular user, and activity of the particularuser.